Platform Train Settings Worksheet

This optional worksheet is similar to the Origin Settings worksheet but is designed specifically for use with LEGION’s Platform-Train Interface features.

Many aspects work the same as the Origin Settings worksheet, but the Platform-Train Settings worksheet has some important differences:

Each table defines a named Platform, corresponding to a LEGION Platform object.
Named Train Services are associated with each Platform. These Services can be named as Origins and/or Final Destinations in the OD Matrix worksheet.
Platform-specific EDOT (Effective Door Open Time) configuration is provided, which determines the departure times of all Services leaving the Platform. (Note: in case of Services with different EDOTs at the same Platform, individual Services’ Availability Profiles may be edited in the Edit Data Profiles dialog box in LEGION Model Builder.)

To adjust the desired number of tables in the Platform-Train Settings worksheet, from the Add-ins menu, click the smiley face icon, while the Platform-Train settings tab is selected. The Restore Origin Groups dialog box opens.

Note: When using multiple screens, with LEGION Data Template open in a secondary screen, the Restore Origin Groups dialog box opens in the primary screen.

In the Number of Tables to be Restored/Created? field, type the number of Platforms in the model. That number of Platform-related tables are created.

Once a Platform name has been selected, its Services can be added to it.

Create Distribution

Distributions let you define the proportions of arriving entities (alighters and - if separately defined - stayers, too), that will come from different locations along the length of the Train associated with a Service. To define a distribution, select Yes from the Create Distribution? drop-down field and type percentages across cells in a row (left-to-right representing front-to-back of Train, even if reversed), to the level of detail wanted. With no distribution defined, entities originating on a Train are distributed across it evenly.

These distributions appear in LEGION models as Passenger Distributions associated with imported Services.

Note: Passenger Distributions defined here can also be assigned to Platforms, as boarding passenger distributions. This can reduce modelling time if a Service’s alighting and boarding distributions are the same.

Warning: There is a risk of unintended side effects if a Carriage Passenger Distribution is modified and no longer matches the required Platform distribution.

The next sub-table permits definition of a frequency-based timetable, often used by metropolitan transit operators. As well as the Noise and Minimum service interval parameters already present in the Origin Settings worksheet, users can set the EDOT (Effective Door Open Time) to be used at each Platform. At present, this parameter is constant for all Services associated with a Platform. So, to have different EDOTs for different Services arriving at the same Platform, their Availability Profiles must be edited in LEGION Model Builder, once LEGION Data Template is imported.

Availability Profiles based on the randomisation of Services at their Platform may also be specified, for example, if one wanted entities to wait in front of an announcement board until five minutes before Service departures, to represent platform announcements in a mainline station hall.

Before importing LEGION Data Template, using the Data Import Manager, ensure that:

Services in LEGION Data Template are already defined in the model
Trains are assigned to Services
Services are assigned to Platforms

Train type must be defined for each Service. Once this is done, the Data Import feature automatically generates Service timetables and assigns the correct number of alighters, boarders and stayers to each Service.